home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 19
/
Night Owl (The Best of Shareware)(NOPV 19)(1996).ISO
/
007a
/
statsp4c.zip
/
CLEANUPP.DOC
< prev
next >
Wrap
Text File
|
1996-01-01
|
12KB
|
230 lines
CleanUpP for Postlink Logs
═════════════════════════════════════════════════════════════════
**** Information **** CleanUp is no longer included in this
archive, nor is it supported by this author. It has been replaced
with a whole new program called CleanUpP. It does not run like
CleanUp. If you want to continue using CleanUp it may or may not
find the newer STATUSP.EXE files as valid. If so it will not run
without this verification.
CleanUpP does not run without the registration of StatusP!
CleanUpP was written to reduce the size of the Postlink
log(s) to speed up the running of StatusP as well as reducing the
size of the Postlink log(s) for editing, archiving, etc. This
program is written to be run in conjunction with my StatusP
program and is not to be run as a separate program. To do so is
in violation of my copyright.
This archive should contain the following files:
CLEANUPP.EXE.......... Postlink log reduction utility
CLEANUPP.DOC.......... Instructions for running CleanUpP
DOORS.TXT............. Current list James Huckabey doors
FILE_ID.DIZ........... BBS description file
SOFTWARE.TXT.......... Information about shareware
HUCKABEY.TXT.......... Current list of all James Huckabey
software.
READ.ME............... Update/changes information
STATUSP.BAT........... Sample batch file
STATUSP.EXE........... Actual program
STATUSP.DOC........... Instructions for running StatusP
STATUSP.CFG........... Sample configuration file
STATUSP2.CFG.......... Sample configuration file
STATUSP3.CFG.......... Sample configuration file
ARCHIVE.TXT........... This list of files
******* WARNING *******
A word of caution: Because garbage can get into any/all logs
it is possible to have CleanUpP chop off your log with an invalid
end of file marker. That is the garbage can contain a EOF marker
and CleanUpP believes that this is the end of the file and cuts
off the log at that point. There is no way to program around this
problem. Once the marker is found the file is set as the end and
no way I can work out and over come a premature end of file
marker. I am still trying to work this out.
******* o *******
Syntax: CleanUpP [path]POSTLINK.LOG [path][OTHER.CFG]
Where POSTLINK.LOG is your Postlink log file name.
Where [path][OTHER.CFG) is the name of your StatusP
configuration if you are not using 'STATUSP.CFG' for the name of
the configuration file(s). If you do not supply the name that you
use CleanUpP searches for and aborts if it cannot find the
default STATUSP.CFG file. Make sure you supply any name changes.
For best results CleanUpP should be run before StatusP. That
way on the day of the rollover the LOG(s) is/are at their
smallest possible size. If you run CleanUpP a second time on a
log produced by rollover it does a hasty exit if the first date
found is the current date. No harm done, nothing changed!
After rollover you can run CleanUpP on your previous log to
remove the last day's activity. To do this you would unarchive
the rollover archive, run CleanUpP on your log(s) and rearchive
the logs. This way the log only contains conference names and
Import / Export totals with header (start date) and trailer (end
date). If you were viewing previous activity this would make it
much easier to read and total up.
CleanUpP must be in current directory or somewhere in your
path statement. You may include a full name and path to your log
file. It removes everything but the current activity and writes
out the new import and export information and running totals for
each conference.
At the end of activity the program displays the starting and
ending log file sizes, starting and ending line count. The
process may be lengthy depending on the size of your log. It
should be run daily. All that is needed to run CleanUpP is as
much free space on the log file drive as the size of the log or
the program does create a new log.
Separate Export Import and Import Problems
If you use separate logs for Export and Import you will get
Import conferences showing zero messages in your Export log. I
have found no way to program around this short of making more
command line options or another configuration file. I thought it
best to keep those options to a minimum. At most this would be as
many lines as there are Export conferences. Exporting is where
cleanUpP gets the conference count. If separate logs you do not
get conferences without messages in your Import log without the
presence of Export conferences for count. As with StatusP, the
only way to find out how many conferences there are is to use
Export activity since only there are all conferences listed.
Imports only show actual imports with messages whereas Exports
shows all current BBS conferences regardless of message count.
Do You Have To Run CleanUpP?
If your BBS system is critical on free space you can run
CleanUpP everyday to reduce the size of your Postlink log(s). The
program removes unneeded lines and does nothing to the current
day's portion of the log. It stops processing data when it finds
the log date equal to the system date.
If your hard drive space it not at a premium or speed is not
critical then you really do not have to run CleanUpP. Or of
course you want all information to remain in the log. The main
savings on time, both CleanUpP and StatusP, would be gained the
most near month's end. It takes StatusP time to read in and
process logs when they are larger. Lines can reach 18,000 or more
on a system with a lot of conferences and/or messages.
When using CleanUpP the size of the log on the 2nd day of
the month would be the same as the size on the last day of the
month. Perhaps a few bytes larger or a line count may change do
to added conferences.
What CleanUpP does is read in all lines separating out the
conference names and number of messages per conference (running
total for each conference). When the program finds the date in
the log matches the system date, or reaches end of log, it starts
writing out the conference names and total messages per
conference to a new log. If it has found today's date then it
appends the rest of the current data to the new log. When
finished it erases the old log.
This leaves you with a new log showing only the totals per
conference, in sorted order, then the start of the current day's
activity (unaltered). CleanUpP only needs to be run once per day.
If you run it additional times nothing is changed in the log
although it does keep writing out a new one. Any additional
information written to the log will not be processed until the
next day.
If the month rolls over in the log CleanUpP does nothing and
exits immediately. StatusP then does the rollover during it's own
activities.
Regardless of what is deleted the current day's activities
are not altered in any way unless premature end of file (EOF)
marker.
Special Bulletins Showing Totals Each Conference
It is possible to make a "Previous Month's" activity
bulletin out of the rolled over log(s). At least the data would
be all there and compacted. All you have to do is make a special
STATUSP.CFG file with the name of the bulletins for these special
monthly Bulletins. You could do one each month for the previous
month. The bulletin for the Last Import could just be written to
the current directory and not used. For a full month the
Bulletins would have something like 01-01-95 to 01-31-95 for the
time period as this would be the dates in a log for January 1995.
Of course the above would work even if you did not run
CleanUpP.
This Program
If you don't like the program please write to me and explain
why. Send me any suggestions you might have. If they enhance the
overall program I will try to incorporate part, some, all, in the
next release.
Errors
Errors are written to the current directory in a file called
CLEANUPP.ERR. If the file already exists additional errors are
appended to the end of the file. It may be deleted after you have
made note of any errors. It's existence it not required by the
program. Current directory is wherever you call CLEANUPP.EXE
from.
CleanUpP must find a valid and registered copy of
STATUSP.EXE either in the current directory, path or set in the
environment according to the StatusP documentation. CleanUpP
reads in the STATUSP.CFG file, or optional command line
configuration file. I did this because some people might want to
run this program on their log file without having StatusP on
their system. This is in violation of my copyrights. This program
can only be run in conjunction with STATUSP.EXE.
CLEANUPP.EXE or any of the other files in the archive may
not be distributed in any form other than the original archive
and unaltered.
Please support my efforts and register StatusP, which
includes making CleanUpP operational. See STATUSP.DOC for
details.
James Huckabey
3621-A Fraser Street
Bellingham, Washington 98226-2473 U.S.A.
(360) 671-2868, voice, Pacific
I do have a US Robotics HST DS 14.4 v32, v42, v42bis modem!